Google Links

Follow the links below to find material targeted to the unit's elements, performance criteria, required skills and knowledge

Elements and Performance Criteria

1. Determine the software fault to be corrected
   • Collect and review the software fault details from sources
   • Obtain technical data to assist in identifying the problem
   • Clarify nature of the problem with appropriate person where necessary
2. Identify and isolate the fault
   • Review program documentation for specific modules in order to pinpoint problem areas
   • Review the source code for logic errors
   • 2.3 Read manuals, help files and 'read me files' to determine if there is a known fix
   • Undertake additional testing to identify or duplicate fault
   • Escalate the difficult faults that cannot be identified
3. Design a fix for the fault
   • Ensure that the requirements needed to fix the fault are understood by the client
   • Consider alternative options and choose the most effective solution
   • Consider the possible impact of the fix on other parts of the system
   • Document the changes according to the organisational guidelines
4. Carry out the fix to the software
   • Identify, and obtain, access to the appropriate software development tools, source code, and libraries
   • Construct the appropriate code to correct the fault, according to organisational and programming standards
   • Compile, or regenerate, the code for changed programs and the associated modules
   • Correct, and resubmit, the code until error free
   • Document the changes, according to organisational and programming standards
5. Test the fix and associated system areas
   • Check logic to ensure that it works with test data, corrects original fault, and does not cause problems elsewhere
   • Request users to perform acceptance testing and record outcomes
6. Hand over to systems operations area
   • Update the documentation to reflect all the changes made
   • Confirm acceptance by systems operations and arrange for sign-off, according to procedures

Performance Evidence

Evidence of the ability to:

effectively maintain custom software

apply a fix that works

deploy a possible range of solutions to produce the same results.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

---

Knowledge Evidence

To complete the unit requirements safely and effectively, the individual must:

explain the concepts relating to analysing a system performance compared with the system’s current functionality

describe the processes and procedures relating to testing software systems

describe current industry-accepted hardware and software products, as they relate to system maintenance

specify the programming code required for the project

describe the program documentation required

describe the impact of changes on applications and systems

identify and summarise the programming standards relating to custom software.

---